It seems that in the original logic we updated all internal dependencies to their equivalents under the @metamask-previews namespace. That no longer happens now, but is it something we want to do? Or... do we already handle that somewhere 🤔

In the new workflow, the user of the new preview packages is expected to use resolutions to update any packages that are relevant to what they are testing. The resolutions serve that purpose now instead.

There is a bit of a footgun here still in that you can forget to update the resolutions. But updating them manually in the preview manifests would also be a footgun, as it would force the extension to update each transitive dependency when they otherwise would have been in-range (which could prevent us from noticing that we forgot to release something critical). Either way has risks.

Though regardless, this code being deleted here doesn't do anything today, so we can remove it and consider replacing it with something later if we think it's necessary.